Skip to content

feat(threads): founder inboxes from owner and type tags - #57

Open
nullStack65 wants to merge 1 commit into
mainfrom
cursor/founder-inbox-tags-2efa
Open

nullStack65 wants to merge 1 commit into
mainfrom
cursor/founder-inbox-tags-2efa

Conversation

@nullStack65

Copy link
Copy Markdown
Owner

What Changed

Threads in the shared pool can carry three optional tags:

  • owner: free-form string. The sidebar suggests Kameron, Jeff, Lead, and Jeff's Lead, and any browser can add more names.
  • threadType: needs-human, fyi, or bot-work.
  • startedBy: who opened the thread, same free-form identity space.

They can be set on thread.create and on thread.turn.start bootstrap createThread, and changed later with thread.meta.update (pass null to clear). The web sidebar (desktop uses the same UI) has an inbox picker, a show/hide control for bot work, and defaults stamped onto threads that browser starts. The thread action menu sets owner and type on an existing thread. Search reveals bot-work threads inside the current inbox. Mobile hides bot-work unless the list is searching.

The t3-code MCP server exposes set_thread_routing so a bot in a thread can tag that thread or another thread id.

Untagged threads omit the fields. With "All threads" selected they stay on the list they are on today.

Audit

T3 cannot filter a shared pool by person today.

  • Lifecycle that exists: archive, settle / un-settle, snooze / wake, pin / unpin, reorder, mark unread (a client visit timestamp), delete.
  • There is no label, tag, assignee, owner, or work-type field on a thread.
  • There is no createdBy or creationSource. historyImport only marks an imported transcript. executionScope is coding or coordinator. Pull-request author is the PR author, not who started the thread.
  • The running orchestrator tools (t3_thread_list, t3_thread_organize, t3_thread_launch, create_threads, t3_thread_update, t3_thread_configure) are not in this fork. They live in upstream T3. A live check of those tools (Nov 14, 2026) matches the source gap: lists filter by project, run status, title text, settled, and snoozed. Organizing is pin, snooze, settle, archive, and mark unread.
  • This fork's agent MCP is t3-code: preview, device, and pull requests. Sidebar sections are pinned, active, snoozed, settled, and archived.

Stopgap before this ships

Keep bot-only work in its own project, and auto-settle those threads when the turn finishes. Settled threads leave the active list, and t3_thread_list with settled=true is how to find them again. That uses today's project scope and settlement. It does not give each founder an inbox.

How bots should tag

Adopt this in closura-agent-config. The wire names are owner, threadType, and startedBy.

On create (thread.create, or thread.turn.start → bootstrap.createThread, which is what t3_thread_launch and create_threads should pass through once those tools are updated):

  • owner: Kameron, Jeff, Lead, Jeff's Lead, or any other non-empty name
  • threadType: needs-human, fyi, or bot-work
  • startedBy: the identity that opened the thread

Later, call set_thread_routing on the t3-code MCP server, or send thread.meta.update with the same fields. Omit a field to leave it. null clears it.

Until the upstream orchestrator tools accept those fields, bots on this fork tag with set_thread_routing after the thread exists.

Founder inbox rule: show a thread when owner is me, or threadType is needs-human and owner is me, or startedBy is me. bot-work stays hidden until "Show bot work" or a search. Untagged threads stay on All threads.

Why

One shared T3 pool, with each founder's inbox as a filter, instead of a separate compute pool per person or bot.

UI Changes

Sidebar inbox picker, bot-work toggle, and new-thread owner/type defaults. Thread menus gain Set owner and Set type. No screenshot in this run: the dev server was not paired, so the check was the filter tests and typecheck rather than a browser pass.

Checklist

  • This PR is one concern: inbox tags
  • I explained what changed and why
  • I included before/after screenshots for any UI changes
  • I included a video for animation/interaction changes

Verification

GitHub Actions are disabled on this fork. Local results, Node 24.13.1, vp 0.3.3:

  • vp run -r --concurrency-limit 2 typecheck: 15 packages, exit 0. Effect diagnostics are suggestions only.
  • vp lint: exit 0. Remaining output is existing warnings.
  • Tests that cover this change passed: client-runtime 1584, web unit 5409, mobile 1686 passed (5 skipped), server inbox/decider/MCP/projection/snapshot tests included in the server run.
  • vp run -r test stopped on packages/shared/src/isolationRoot.test.ts (expected message unowned files, got an ownership/private-profile error). That file is untouched.
  • apps/server: 5712 passed, 11 skipped, 1 failed: scripts/deploy-relay-workflow.test.ts expects only the nullStack65 repository identity and the workflow now also names kameron-smith-closura. Untouched by this PR.
  • apps/desktop: 1353 passed, 4 suites failed loading because Electron.app is undefined while the Electron binary was downloading. Untouched by this PR.

Provenance

Model: Grok 4.7
Task: feature

Open in Web Open in Cursor 

Shared threads can record who they are for, what kind of work they are, and who started them. Founder inboxes hide bot-to-bot threads until search or a toggle asks for them, and untagged threads stay on the shared list.

Model: Grok 4.7
Task: feature
Agent: cursor
Co-authored-by: Kameron Smith <nullStack65@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Nov 14, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@nullStack65

Copy link
Copy Markdown
Owner Author

Frozen 2026-11-22 CEO portfolio audit — cash-path priority; can reopen at the Dec 18 runway check.

@nullStack65 nullStack65 reopened this Nov 22, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants